System and method for creating a short message system usage record

ABSTRACT

A method of creating an email usage record is provided. An input signal is received. An email usage record is created in response to the received input signal. An event jacket is created. The event jacket is associated with the email usage record. A command to send an email message is received. A confirmation signal is received after the email message has been sent. Finally, an email leg jacket is created. The email leg jacket includes at least one record. The at least one record includes information relating to the email message.

FIELD OF THE INVENTION

[0001] The present invention generally relates to communication systems,and, more particularly, to methods and systems for creating email usagerecords.

BACKGROUND OF THE INVENTION

[0002] In today's communication environment, telephone calls are usuallyplaced through a telecommunication network. When a telecommunicationnetwork detects a telephone call, a call detail record, which tracks theusage of services offered by the telecommunication carrier and recordsvarious details associated with the call, is created. Typically, thecall detail record includes, for example, such items as the callednumber, the calling number, the date, the time, the duration of the calland other information relating to the call.

[0003] The call detail record may be stored in accordance with any oneof a number of formats, such as, the Data Message Handling (DMH)standard. The DMH standard generally includes five data-containingjackets: an activity jacket, a call jacket, a segment jacket, an eventjacket and a leg jacket. Activity jackets contain radio resource usagedata, which may include, for example, the frequency on which a wirelessdevice is operating. Call jackets contain a record of the type ofservices used during a call. Segment jackets contain a record ofcommunication network facility usage data, including, for example, trunkgroup usage and switch identifier usage. Event jackets contain a recordof the time and date the end user accessed the communication network, aswell as an authorization identifier. Finally, leg jackets contain arecord concerning the routing of the call.

[0004] However, the DMH standard typically records data concerning voicecalls, and may not address other telephone services, including, forexample, email services, paging services, end user-location detectionservices, content delivery services, and the services from other typesof network elements. Further, call detail records are created after thecall is terminated.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005]FIG. 1 is a block diagram of an embodiment of a communicationsystem in accordance with the present invention;

[0006]FIG. 2 is a depiction of an email usage record in accordance withthe present invention;

[0007]FIG. 3 is a flowchart of an embodiment of an email record creationroutine in accordance with the present invention; and

[0008]FIG. 4 is an exemplary block diagram of another embodiment of acommunication system in accordance with the present invention.

DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EMBODIMENTS

[0009]FIG. 1 is a block diagram that illustrates an embodiment of acommunication system 10. The communication system 10 generally includesone or more network access devices or communication devices 12, 22,communication networks 14, 18 and a communication node 16. As furtherdescribed below, the communication system 10 can provide variousservices and capabilities to cellular end users, wire-line telephone endusers, paging end users, satellite end users, mobile or portabletelephone end users, trunked end users, computer network end users(e.g., Internet or Intranet end users), wireless data end users, branchoffice end users and the like. The communication system 10 can alsocreate an email record for recording the details of an e-mailtransaction, as further described below.

[0010] The communication devices 12, 22 of the communication system 10can be utilized by end users 20, 32 to access and/or connect with thecommunication node 16. The communication devices 12, 22 can include, butare not limited to, wireline telephones, mobile telephones, pagingunits, radio units, wireless data devices, Web telephones, portable orwireless telephones, personal information managers (PIMs), personaldigital assistants (PDAs), personal computers (PCs), network televisions(TVs), Internet TVs, Internet telephones, portable wireless devices(i.e., two-way pagers), security systems (both mobile andpremises-based), workstations or any other suitable communicationdevices.

[0011] The communication devices 12, 22 communicate with thecommunication node 16 via the communication networks 14, 18. Thecommunication networks 14, 18 can interface with the communicationdevices 12, 22 through wireline or wireless networks or systems (i.e.,telephone or televisions systems, Integrated Services Digital Network(ISDN) systems, coaxial lines, computer networks, digital end userlines, private networks, wireless local loop systems, etc.).

[0012] The communication networks 14, 18 of the communication system 10can include, but are not limited to, intranets, extranets, the Internet,a Local Area Network (LAN), a telephone network, (e.g., a PublicSwitched Telephone Network (PSTN), private telephone networks, etc.), acellular network, satellite networks, a personal communication system, aTV network (e.g., a cable TV system), local, regional, national orglobal paging networks, an email system, a wireless data network (e.g.,satellite data or local wireless data networks), a wireless LAN, awireless local loop/distribution system (e.g., LMDS, MMDS or CodeDivision Multiple Access (CDMA) based system), a Voice Over InternetProtocol (VoIP) network, or any other suitable network. Thecommunication networks 14, 18 can also include a wide area network(WAN), such as, for example, the Internet, the World Wide Web (WWW) orany other similar on-line service. It will be recognized that thecommunication networks 14, 18 may have portions in common, may comprisetwo separate networks, or may be the same network.

[0013] The communication node 16 of the communication system 10 caninclude, but is not limited to, an interactive voice response node, aserver computer, the MIX™ platform and the Myosphere™ Service providedby Motorola, Inc. of Schaumburg, Ill. (as further described withreference to FIG. 4), or other suitable system. It will be recognizedthat the communication node 16 may be integrated within or may be remotefrom the communication networks 14, 18.

[0014] The communication node 16 records and maintains a call detailrecord, as well as an email usage record. The email usage record storesinformation about each email transaction performed by the end userwithin the communication system 10. For example, each time the end usersends an email message, the communication node 16 will record an emailusage record. Preferably, each email usage record is stored withinmemory or a database, which may be located integral with or remote fromthe communication node 16.

[0015]FIG. 2 depicts an email usage record 100. The email usage record100 is preferably comprised of a set of data-containing jackets, witheach jacket including a number of records. Each record may include anumber of sub-records, as further described below. The email usagerecord 100 may be compatible with any suitable standard, such as the DMHstandard.

[0016] The email usage record 100 preferably includes an event jacket101 and an email leg jacket 109. The event jacket 101 and email legjacket 109 may be compatible with the DMH standard, the AutomaticMessage Accounting standard, the Bellcore Account Format standard or anyother suitable standard.

[0017] The event jacket 101 and the email leg jacket 109 may includemandatory and/or optional parameters and fields depending on theoperation of the communication system 10. The event jacket 101preferably contains various information relating to the identity of theend user and the communication device, the time and/or date of thetransaction, etc. It will be recognized that the event jacket 101 maycontain any other suitable information. The email leg jacket 109preferably includes the details of email transactions made by an enduser, such as a destination email address, a source email address, theemail size, attachments, the email provider, the email urgency, thedelivery schedule, the email classification, the reoccurrence of theemail, recipients, the creation time and date and any delivery receipts.Thus, the email usage record 100 preferably contains an event jacket101, and may contain, dependent upon the number of email transactions,one or more email leg jackets 109.

[0018] As shown in FIG. 2, the event jacket preferably includes an enduser identification record 102, an end user number identification record104, an event jacket creation time record 106 and an event jacketcreation date record 108. The end user identification record 102 may bea record identifying the sender of the input signal, such as the enduser. The end user identification record 102 may also indicate whetherthe end user is authorized to use the features and services of thecommunication system (i.e., whether the end user is a subscriber to thecommunication system). Preferably, the communication node compares theinput signal with stored data concerning the end user. For example, theend user may be required to input a Personal Identification Number, acalling line identifier, a password or Internet “cookies” or tokens.

[0019] The end user device identification record 104 maintains andauthenticates the number of the communication device from which the enduser is calling. Preferably, the communication node performs acomparison between the number received in the input signal and thestored end user identification record. Upon finding a match, thecommunication node continues to create the email usage record 100. Theevent jacket creation time record 106 is preferably a record of the timeat which the input signal was received at the communication node (whichalso coincides with the time of the creation of an email usage record100).

[0020] The event jacket creation date record 108 preferably correspondsto the calendar date on which the input signal was received by thecommunication node (also coinciding with the creation of the email usagerecord 100). The communication node, when accessing an internalelectronic clock, may create the event jacket creation time and daterecords 106, 108.

[0021] The email leg jacket 109 of the email usage record 100, which mayinclude a link to the event jacket, preferably includes a number ofrecords, such as, for example, an email leg jacket identifier record110, a destination email address record 112, a source email addressrecord 114, an email size record 116, an attachment record 118, an emailprovider record 120, an email urgency record 122, a delivery schedulerecord 124, an email classification record 126, a reoccurrence record128, a recipient record 130, an email leg jacket creation time record132, an email leg jacket creation date record 134, a delivery receiptrecord 136 and a bill-to record 136. Preferably, the email leg jacketincludes data collected from the instruction signal, the confirmationsignal and the email message itself.

[0022] The email leg jacket identifier record 110 preferably identifiesthe email leg jacket 109 as an email message. Additionally, the emailleg jacket identifier record 110 may include a link to the event jacket101 of the current transaction. This link provides an organizationalreference to the event jacket 101. As a result, if the email leg jacket109 is stored in a location apart from the event jacket 101, there is anindication as to which transaction the email leg jacket 109 corresponds.

[0023] The destination email address record 112 preferably includesinformation relating to the email address to which the email message wassent. The destination email address record 112 may include a number ofsub-records, including, for example, an identifier sub-record, whichpreferably identifies the destination address signal as containing adestination email address, and a printable string sub-record, which maycomprise a text version of the destination email address.

[0024] The source email address record 114, relating to the emailaddress of the end user, is preferably derived from the end user'saccount with the communication node. Similar to the destination emailaddress record 112, the source email address record 114 preferablyincludes information relating to the email address from which the emailmessage was sent. The source email address record 114 may include anumber of sub-records, including, for example, an identifier sub-record,and a printable string sub-record.

[0025] The email size record 116 preferably comprises informationrelating to the size of the sent email message. The email size record116 may include a positive integer sub-record comprising the size of theemail message, including, for example, the number of words or charactersin the email message, the byte size of the email message, etc.

[0026] The attachment record 118 preferably includes informationrelating to any attachments that were sent with the email message. Thisinformation may include the number, size and type of the attachments.The attachment record 118 may include an identifier sub-record, a numbersub-record specifying the number of attachments included with the emailmessage, a size sub-record specifying the size of the attachments, and atype sub-record, specifying the type of the included attachments,including, for example, a word processing document, a spreadsheet or afile containing the voice message.

[0027] The email provider record 120 preferably includes informationrelating to the Internet Service Provider (ISP) that transmits the emailmessage. The email provider record 120 may include an identifiersub-record and a printable string sub-record, which comprises the nameof the email provider. The email provider record 120 may includeinformation relating to the email service provider, including, forexample, the name of the provider, the cost, the quality of service orthe time sensitivity of the email message.

[0028] The email urgency record 122 preferably includes informationrelating to the priority of the delivery of the email message thatcorresponds to how quickly the sender wishes the email message to besent. For example, a value of “1” may signify that the email messageshould be sent as soon as possible, a value of “2” may correspond tonormal delivery, a value of “3” may indicate to the email provider tosend the message at the lowest cost possible, and a value of “0” mayindicate an unknown or unspecified urgency rating. The priority of theemail message may be pre-determined by the sender of the email messageor may be determined by the communication node. The email urgency record122 may also include an identifier sub-record as well as a valuesub-record corresponding to the urgency of the email message.

[0029] The delivery schedule record 124 preferably includes informationrelating to when the email message should be sent. The delivery schedulerecord 124 may include an identifier sub-record, a request datesub-record, a request time sub-record, a delivery date sub-record, adelivery time sub-record, a request execution date sub-record, a requestexecution time sub-record and a reoccurrence sub-record. The requestdate sub-record preferably specifies the date when the transactionrequest was made. The request time sub-record preferably specifies thetime at which the transaction request was made. The delivery datesub-record preferably specifies the date of desired delivery of theemail message. The delivery time sub-record preferably specifies thetime of desired delivery of the email message. Finally, the reoccurrencesub-record preferably specifies whether the email message shouldreoccur; that is, whether the email message will be sent more than once.

[0030] The email classification record 126 preferably comprisesinformation relating to the classification of the email message. In thisembodiment, email classification may be similar to classification oftraditional mail, in which one class, for example, is designated foradvertisements, and another class is designated for business mail. Theemail classification 126 may include an identifier sub-record as well asa value identifier sub-record corresponding to the class of the emailmessage. For example, values may indicate that the email message is anadvertisement. Other values may signify business class, non-businessclass or confidential email messages. Furthermore, other values maytrigger additional information, including for example certified(requiring the certification by the system of email dispatch anddelivery) or registered email messages (requiring dispatch and deliverycertification by the system and certification by the recipient ofreceipt of the email message).

[0031] The reoccurrence record 128 preferably comprises informationrelating to whether the email message is to be sent more than once. Thereoccurrence record 128 may include an identifier sub-record. Inaddition, the reoccurrence record 128 may include a value sub-recordcorresponding to the reoccurrence of the email message. For example,values may indicate the email message be sent once, etc. daily, weekly,etc.

[0032] The recipient record 130 preferably comprises informationrelating to the total number of recipients receiving the email message.The recipient record 130 may include an identifier sub-record and apositive integer sub-record corresponding to the number of emailrecipients.

[0033] The email leg jacket creation time record 132 is preferably arecord of the time at which the email message was sent. The email legjacket creation date record 134 preferably corresponds to the date onwhich the email message was sent. As is the case with the event jacketcreation time and date records, these two records may be obtained viathe access of an internal electronic clock.

[0034] The delivery receipt record 136 will preferably contain a recordspecifying whether the transmitted email message requires a receipt ofdelivery notification, i.e., a notice to the sender that the emailmessage was delivered to and/or received by the recipient.

[0035] The bill-to record 138 preferably contains a record of whichparty, if any, will be billed for the transmission of the email message.The bill-to record 138 may be a “collect on delivery” type of record incases in which the receiving party is charged for receiving the emailmessage, as sending soft products via email or providing services usingemail are good candidates for the receiver to pay the fare. The bill-torecord 138 may contain one or more of the following “billees:” thesender, the receiver or the third party.

[0036]FIG. 3 illustrates an embodiment of a routine for creating anemail usage record. At block 500, the communication node receives aninput signal from the communication device. The input signal ispreferably received when the end user accesses the email services of thecommunication node, such as, for example, dialing into the communicationnode from a communication device. The input signal may include atelephone number, an Electronic Serial Number (ESN), a login name orpassword (as in the case of a PC), or any other presently known methodof accessing the communication node.

[0037] Once the input signal is received at the communication node, anemail usage record or event jacket is created at block 510. One exampleof an email usage record is shown in FIG. 2. The communication nodepreferably collects identification data from the input signal, such asthe telephone number and the ESN, as well as from an internal electronicclock, and stores the identification information in the event jacket.

[0038] After creating the email usage record, the end user may perform avariety of tasks or transactions, which may include, for example,sending an email message, preferably commenced by the reception of acommand signal at a communication node at block 520. The communicationnode may receive the instruction signal from a communication device. Forexample, the end user may transmit a command message to thecommunication node instructing the communication node to send an emailmessage, such as, for example, “Send email message to John Doe.”

[0039] Alternatively, the communication node itself may generate theinstruction signal. This may occur when, for example, the communicationnode is pre-programmed to transmit an email alert or a schedulenotification. For example, the end user may program the communicationnode to schedule an email delivery at 6:00 a.m. tomorrow. In this case,the event jacket and the email leg jacket are created when the end userinstructs or programs the communication node to perform suchtransaction.

[0040] Once the communication node determines (or generates) a commandsignal, the communication node begins recording information to the emailusage record. After the email message has been sent, the communicationnode then receives a confirmation signal at block 530. The confirmationsignal indicates that the email message has been sent. The reception ofthe confirmation signal at the communication node will preferablytrigger the communication node to complete the collection of datanecessary to complete the email leg jacket at block 540.

[0041] Referring now to FIG. 4, an exemplary block diagram of anotherembodiment of a communication system 200 having the capability to createand maintain email usage records is illustrated. The communicationsystem can implement the routine described in FIG. 3 above.

[0042] The communication system 200 generally includes one or morecommunication devices 201, 202, 203, 204, 205 (five being shown), anelectronic network 206, and one or more information sources (e.g.,content providers 208, 221 (two being shown) and data and voice markuplanguage servers 209, 251, 253, 257).

[0043] The end user can access the electronic network 206 by dialing asingle direct access telephone number (e.g., a foreign exchangetelephone number, a local telephone number, or a toll-free telephonenumber or PBX) from the communication device 201. The end user can alsoaccess the electronic network 206 from the communication device 202 viathe Internet 220 or WWW, from the communication device 203 via a pagingnetwork 211, or from the communication device 205 via a LAN, a WAN, anemail connection or in any other similar manner.

[0044] As shown in FIG. 4, the electronic network 206 includes atelecommunication network 210 and a communication node 212. Thetelecommunication network 210 is preferably connected to thecommunication node 212 via a high-speed data link, such as, for example,a T1 telephone line, a LAN, a WAN or a VoIP network. Thetelecommunication network 210 preferably includes a PSTN 214 and acarrier network 216. The telecommunication network 210 can also include,for example, international or local exchange networks, cable TVnetworks, inter-exchange carrier or long distance carrier networks,cellular networks (e.g., mobile switching centers), PBXs, satellitesystems, wireless data networks and other switching centers such asconventional or trunked radio systems (not shown), etc. The electronicnetwork 206 can also include additional telecommunication networks, suchas, for example, a wireless data network 207.

[0045] The PSTN 214 can include various types of communicationequipment, such as, for example, ATM networks, Fiber Distributed Datanetworks (FDDI), T1 lines, cable TV networks, VoIP networks and thelike. The carrier network 216 generally includes a telephone switchingsystem or central office 218.

[0046] It will be recognized that the carrier network 216 can be anysuitable system that can route calls to the communication node 212, andthe central office 218 can be any suitable wire-line or wirelessswitching system.

[0047] The communication node 212 is preferably configured to receiveand process incoming calls from the carrier network 216 and the Internet220. The communication node 212 can receive and process pages from thepaging network 211 and can also receive and process messages (e.g.,emails) from the LAN, WAN, wireless data or email system 213.

[0048] When an end user dials into the electronic network 206 from thecommunication device 201, the carrier network 216 routes the incomingcall from the PSTN 214 to the communication node 212 over one or moretelephone lines or trunks. The incoming calls preferably enter thecarrier network 216 through one or more “888” or “800” Inward Wide AreaTelecommunications Services trunk lines, local exchange or long distancetrunk lines. It is also contemplated that the incoming calls can bereceived from a cable, cellular or VoIP network or any other suitablesystem.

[0049] The communication node 212 answers the incoming call from thecarrier network 216 and retrieves an appropriate announcement (e.g., awelcome greeting) from a database, server or browser. The communicationnode 212 then plays the announcement to the caller. In response to audioinputs from the end user, the communication node 212 retrievesinformation from a destination or database of one or more of theinformation sources, such as the content providers 208, 221 or themarkup language servers 209, 251, 253, 257. After the communication node212 receives the information, it provides a response to the end userbased upon the retrieved information.

[0050] The communication node 212 can provide various dialog voicepersonalities (e.g., a female voice, a male voice, etc.), and canimplement various grammars (e.g., vocabulary) to detect and respond tothe audio inputs from the end user. In addition, the communication node212 can automatically select various speech recognition models (e.g.,English, Spanish or English accent models) based upon an end user'sprofile, communication device and/or speech patterns. The communicationnode 212 can also allow the end user to select a particular speechrecognition model.

[0051] When an end user accesses the electronic network 206 from acommunication device 201, 202, 203, 204, 205 registered with the system(e.g., home telephone, work telephone, cellular telephone, etc.), thecommunication node 212 can by-pass an end user screening option andautomatically identify the end user (or the type of communicationdevice) through the use of ANI or CLI. After the communication node 212verifies the call, the communication node 212 provides a greeting (e.g.,“Hi, this is your personal agent, Maya. Welcome Bob. How may I helpyou?”). The communication node 212 then enters into a dialogue with theend user, and the end user can select a variety of services offered bythe communication node 212.

[0052] When the end user accesses the electronic network 206 from acommunication device not registered with the system (e.g., a payphone, atelephone of a non-end user, etc.), the communication node 212 answersthe call and prompts the end user to enter his or her name and/or apersonal identification number (PIN) using voice commands or DTMFsignals. The communication node 212 can also utilize speakerverification to identify the particular speech pattern of the end user.If the communication node 212 authorizes the end user to access thesystem, the communication node 212 provides a personal greeting to theend user (e.g., “Hi, this is your personal agent, Maya. Welcome Ann. Howmay I help you?”).

[0053] The communication node 212 then enters into a dialogue with theend user, and the end user can select various services offered by thecommunication node 212. If the name and/or PIN of the end user cannot berecognized or verified by the communication node 212, the end user willbe routed to a customer service representative.

[0054] Once the end user has accessed the communication system 200, theend user may implement a wide variety of services and features by usingvoice commands, such as, for example, voice dialing, voice paging,facsimiles, caller announcements, voice mails, reminders, callforwarding, call recording, content information (e.g., newspapers,etc.), read email, read calendars, read “to-do” lists, banking,e-commerce. The communication system 200 can place outbound calls andpages to business and personal parties or contacts (e.g., friends,clients, business associates, family members, etc.) in response to DTMFsignals or voice commands. The calls can be routed through a telephoneor electronic network to the selected party and the pagers can be sentto a selected party via a paging system. The communication system 200can also receive calls routed through a telephone or electronic network.

[0055] As shown in FIG. 4, the communication node 212 preferablyincludes a telephone switch 230, a voice or audio recognition (VRU)client 232, a VRU server 234, a controller or call control unit 236, anOperation and Maintenance Office or a billing server unit 238, a LAN240, an application server unit 242, a database server unit 244, agateway server or router firewall server unit 246, a VoIP unit 248, avoice browser 250, a voice markup language server 251, a messagingserver 255 and a data markup language server 253. Although thecommunication node 212 is shown as being constructed with various typesof independent and separate units or devices, the communication node 212can be implemented by one or more integrated circuits, microprocessors,microcontrollers or computers which may be programmed to execute theoperations or functions equivalent to those performed by the devices orunits shown. It will also be recognized that the communication node 212can be carried out in the form of hardware components and circuitdesigns and/or software or computer programs.

[0056] The communication node 212 can be located in various geographiclocations throughout the world or the United States (e.g., Chicago,Ill.). The communication node 212 can be operated by one or morecarriers (e.g., Sprint, Qwest, MCI, etc.) or independent serviceproviders (e.g., Motorola, Inc.).

[0057] The communication node 212 can be integrated with the carriernetwork 216 or can be located remote from the carrier network 216. It isalso contemplated that the communication node 212 may be integrated intoa communication device, such as, for example, a wire-line or wirelesstelephone, a radio device, a PC, a PDA, a PIM, etc., and can beprogrammed to connect or link directly to an information source.

[0058] The communication node 212 can also be configured as a standalonesystem to allow end users to dial directly into the communication node212 via a direct access telephone number. In addition, the communicationnode 212 may comprise a telephony switch (e.g., a PBX or Centrix unit),an enterprise network or a LAN. In this configuration, the communicationsystem 200 can be implemented to automatically connect an end user tothe communication node 212 when the end user accesses a communicationdevice.

[0059] When the telephone switch 230 receives an incoming call from thecarrier network 216, the call control unit 236 sets up a connection inthe telephone switch 230 to the VRU client 232. The communication node212 then enters into a dialog with the end user regarding variousservices and functions. The VRU client 232 preferably generatespre-recorded voice announcements and/or messages to prompt the end userto provide inputs to the communication node 212 using voice commands orDTMF signals.

[0060] In response to the inputs from the end user, the communicationnode 212 retrieves information from a destination of one of theinformation sources and provides outputs to the end user.

[0061] The telephone switch 230 is preferably connected to the VRUclient 232, the VoIP unit 248 and the LAN 240. The telephone switch 230receives incoming calls from the carrier network 216. The telephoneswitch 230 also receives incoming calls from the communication device202 routed over the Internet 220 via the VoIP unit 248. The telephoneswitch 230 also receives messages and pages from communication devices203, 205, respectively. The telephone switch 230 is preferably a digitalcross-connect switch, Model LNX, available from Excel SwitchingCorporation, Hyannis, Mass. It will be recognized that the telephoneswitch 230 can be any suitable switch.

[0062] The VRU client 232 is preferably connected to the VRU server 234and the LAN 240. The VRU client 232 processes voice communications, DTMFsignals, pages and messages (e.g., emails). Upon receiving voicecommunications, the VRU client 232 routes the speech communications tothe VRU server 234. When the VRU client 232 detects DTMF signals, itsends a command to the call control unit 236. It will be recognized thatthe VRU client 232 can be integrated with the VRU server 234.

[0063] The VRU client 232 preferably comprises a PC, such as, forexample, a Windows NT compatible PC, with hardware capable of connectingindividual telephone lines directly to the telephone switch 230 orcarrier network 216. The VRU client 232 preferably includes amicroprocessor, random access memory, read-only memory, a T1 or ISDNinterface board, and one or more voice communication processing boards(not shown). The voice communication processing boards are preferablyDialogic boards, Antares Model, available from Dialogic Corporation,Parsippany, N.J. The voice communication boards may include a voicerecognition engine having a vocabulary for detecting a speech pattern.

[0064] The voice recognition engine is preferably a RecServer softwarepackage, available from Nuance Communications, Menlo Park, Calif.

[0065] The VRU client 232 can also include an echo canceler (not shown)to reduce or cancel TTS or playback echoes transmitted from the PSTN 214due to hybrid impedance mismatches. The echo canceler is preferablyincluded in an Antares Board Support Package, also available fromDialogic.

[0066] The call control unit 236 is preferably connected to the LAN 240,and sets up the telephone switch 230 to connect incoming calls to theVRU client 232. The call control unit 236 also sets up incoming calls orpages to the communication node 212 over the Internet 220 and pages andmessages sent from the communication devices 203, 205 via the pagingnetwork 211 and email system 213, respectively. The control call unit236 preferably comprises a PC, such as, for example, a Windows NTcompatible PC.

[0067] The LAN 240 allows the various components and devices of thecommunication node 212 to communicate with each other via twisted pair,fiber optic, coaxial cables or the like. The LAN 240 may use Ethernet,Token Ring or other suitable types of protocols. The LAN 240 ispreferably a 100 Megabit per second Ethernet switch, available fromCisco Systems, San Jose, Calif., and can comprise any suitable networksystem. The communication node 212 may include a plurality of LANs.

[0068] The VRU server 234 is connected to the VRU client 232 and the LAN240. The VRU server 234 receives voice communications from the end uservia the VRU client 232. The VRU server 234 processes the voicecommunications and compares the voice communications against avocabulary or grammar stored in the database server unit 244 or asimilar memory device.

[0069] The VRU server 234 provides output signals, representing theresult of the voice communications processing, to the LAN 240. The LAN240 routes the output signal to the call control unit 236, theapplication server unit 242 and/or the voice browser 250. Thecommunication node 212 then performs a specific function associated withthe output signals.

[0070] The VRU server 234 preferably includes a TTS unit 252, anautomatic speech recognition (ASR) unit 254, and a STT unit 256. The TTSunit 252 receives textual data or information (e.g., email, web pages,documents, files, etc.) from the application server unit 242, thedatabase server unit 244, the call control unit 236, the gateway serverunit 246, the application server unit 242 and the voice browser 250. TheTTS unit 252 processes the textual data and converts the data to voicedata or information.

[0071] The TTS unit 252 can provide data to the VRU client 232, whichreads or plays the data to the end user. For example, when the end userrequests information (e.g., news updates, stock information, trafficconditions, etc.), the communication node 212 retrieves the desired data(e.g., textual information) from a destination of the one or more of theinformation sources and converts the data via the TTS unit 252 into aresponse.

[0072] The response is then sent to the VRU client 232. The VRU client232 processes the response and reads an audio message to the end userbased upon the response. It is contemplated that the VRU server 234 canread the audio message to the end user using human recorded speech orsynthesized speech. The TTS unit 252 is preferably a TTS 2000 softwarepackage, available from Lernout and Hauspie Speech Product NV,Burlington, Mass.

[0073] The ASR unit 254 provides speaker dependent or independentautomatic voice recognition of voice communications from the end user.It is contemplated that the ASR unit 254 can include speaker dependentvoice recognition. The ASR unit 254 processes the voice communicationsto determine whether a word or a speech pattern matches any of thegrammars or vocabulary stored in the database server unit 244 ordownloaded from the voice browser 250. When the ASR unit 254 identifiesa selected speech pattern of the voice communications, the ASR unit 254sends an output signal to implement the specific function associatedwith the recognized speech pattern. The ASR unit 254 is preferably aspeaker independent voice recognition software package, RecServer Model,also available from Nuance Communications. It is contemplated that theASR unit 254 can be any suitable voice recognition unit to detect voicecommunications.

[0074] The STT unit 256 receives voice communications and converts thevoice communications to textual information (e.g., a text message). Thetextual information can be sent or routed to the communication devices201, 202, 203, 204, 205, the content providers 208, 221, the markuplanguage servers 209, 251, 253, 257, the voice browser 250 and theapplication server unit 242. The STT unit 256 is preferably a NaturallySpeaking software package, available from Dragon Systems, Newton, Mass.

[0075] The VoIP unit 248 is preferably connected to the telephone switch230 and the LAN 240. The VoIP unit 248 allows an end user to access thecommunication node 212 via the Internet 220 or VoIP public network usingvoice commands. The VoIP unit 248 can receive VoIP protocols (e.g.,H.323 protocols) transmitted over the Internet 220 or Intranet, and canconvert the VoIP protocols to voice information or data. The voiceinformation can then be read to the end user via the VRU client 232.

[0076] The VoIP unit 248 can also receive voice communications from theend user and convert the voice communications to a VoIP protocol thatcan be transmitted over the Internet 220. The VoIP unit 248 ispreferably a Voice Net software package, also available from DialogicCorporation. It will be recognized that the VoIP unit 248 can beincorporated into a communication device.

[0077] The communication node 212 also includes a detection unit 260.The detection unit 260 is preferably a phrase or key word spotter unit,detecting incoming audio inputs or communications or DTMF signals fromthe end user. The detection unit 260 is preferably incorporated into thetelephone switch 230, but can be incorporated into the VRU client 232,the carrier network 216 or the VRU server 234. The detection unit 260 ispreferably included in a RecServer software package, also available fromNuance Communications.

[0078] The detection unit 260 records the audio inputs from the end userand compares the audio inputs to the vocabulary or grammar stored in thedatabase server unit 244. The detection unit 260 continuously monitorsthe end user's audio inputs for a key phase or word after the end useris connected to the node 212. When the detection unit 260 detects thekey phrase or word, the VRU client 232 plays a pre-recorded message tothe end user. The VRU client 232 then responds to the audio inputsprovided by the end user.

[0079] The billing server unit 238 is preferably connected to the LAN240. The billing server unit 238 can record data about the use of thecommunication node 212 by an end user (e.g., length of calls, featuresaccessed by the end user, etc.). Upon completion of a call by an enduser, the call control unit 236 sends data to the billing server unit238. The billing server unit 238 can subsequently process the data inorder to prepare customer bills. The billing server unit 238 can use theANI or CLI of the communication device to properly bill the end user.The billing server unit 238 preferably comprises a Windows NT compatiblePC.

[0080] The gateway server unit 246 is preferably connected to the LAN240 and the Internet 220. The gateway server unit 246 provides access tothe content provider 221 and the voice markup language server 257 viathe Internet 220. The gateway server unit 246 allows end users to accessthe communication node 212 from the communication device 202 via theInternet 220. The gateway server unit 246 can function as a firewall tocontrol access to the communication node 212 to authorized end users.The gateway server unit 246 is preferably a Cisco Router, also availablefrom Cisco Systems.

[0081] The database server unit 244 is preferably connected to the LAN240. The database server unit 244 preferably includes a plurality ofstorage areas to store data relating to end users, such as, for example,speech vocabularies, dialogs, personalities, end user entered data,email usage records, and other information. Preferably, the databaseserver unit 244 stores a personal file or address book. The personaladdress book can contain information required for the operation of thecommunication system 200, including end user reference numbers, personalaccess codes, personal account information, contact's addresses,telephone numbers, etc. The database server unit 244 is preferably a PC,such as, for example, a Windows NT compatible PC.

[0082] The application server unit 242 is preferably connected to theLAN 240 and the content provider 208. The application server unit 242allows the communication node 212 to access information from adestination of the information sources, such as the content providers208, 221 and the markup language servers 209, 251, 253, 257. Forexample, the application server unit 242 can retrieve information (e.g.,weather reports, stock information, traffic reports, restaurants, flowershops, banks, calendars, “to-do” lists, e-commerce, etc.) from adestination of the information sources. This application server unit 242may include Starfish Software to provide the address book, calendar andto-do lists, and to allow the end user to organize information. Theapplication server unit 242 processes the retrieved information andprovides the information to the VRU server 234 and the voice browser250. The VRU server 234 can provide an audio announcement to the enduser based upon the information using TTS synthesizing or human recordedvoice. The application server unit 242 can also send tasks or requests(e.g., transactional information) received from the end user to theinformation sources (e.g., a request to place an order for a pizza). Theapplication server unit 242 can further receive end user inputs from theVRU server 234 based upon a speech recognition output. The applicationserver unit 242 is preferably a PC.

[0083] The voice markup language server 251 is preferably connected tothe LAN 240. The voice markup language server 251 can include adatabase, scripts and markup language documents or pages. The voicemarkup language server 251 is preferably a PC, such as, for example, aWindows NT compatible PC. It will also be recognized that the voicemarkup language server 251 can be an Internet server (e.g., a SunMicrosystems server).

[0084] The messaging server 255 is preferably connected to the LAN 240,the paging network 211, an email system 213 and a short message system(SMS) 290. The messaging server 255 routes pages between the LAN 240 andthe paging network 211. The messaging server 255 is preferably a PC,such as, for example, a Windows NT compatible PC. The messaging server255 can also provide direct storage. It is contemplated that themessaging server 255 can reside externally from the communication node212.

[0085] The voice browser 250 is preferably connected to the LAN 240. Thevoice browser 250 preferably receives information from the markuplanguage servers 209, 251, 253, 257, the database server unit 244 andthe content providers 208, 221. In response to voice commands or DTMFsignals, the voice browser 250 generates a content request (e.g., anelectronic address) to navigate to a destination of one or more of theinformation sources. The content request can use at least a portion of aUniform Resource Locator, an Internet Protocol, a page request, oremail.

[0086] After the voice browser 250 is connected to an informationsource, the voice browser 250 preferably uses a Transmission ControlProtocol/Internet Protocol connection to pass requests to theinformation source. The information source responds to the requests,sending at least a portion of the requested information, represented inelectronic form, to the voice browser 250. The information can be storedin a database, and can include text content, markup language document orpages, non-text content, dialogs, audio sample data, recognitiongrammars, etc. The voice browser 250 then parses and interprets theinformation, further described below. The voice browser 250 can beintegrated into the communication devices 201, 202, 203, 204, 205.

[0087] As shown in FIG. 4, the content provider 208 is connected to theapplication server unit 242 of the communication node 212, and thecontent provider 221 is connected to the gateway server unit 246 of thecommunication node 212 via the Internet 220. The content providers 208,221 can store various content information, such as, for example, news,banking, commerce, weather, traffic conditions, etc. The contentproviders 208, 221 can include a server to operate WWW pages ordocuments in the form of a markup language. The content providers 208,221 can also include a database, scripts and/or markup languagedocuments or pages. The scripts can include images, audio, grammars,computer programs, etc. The content providers 208, 221 execute suitableserver software to send requested information to the voice browser 250.

[0088] The voice mail unit 274 is preferably connected to the telephoneswitch 203 and the LAN 240. The voice mail unit 274 can store voice mailmessages from parties trying to send messages to the communication node212. When an end user accesses the electronic network 206, the voicemail unit 274 can notify the end user of new and stored messages. Theend user can access the messages to play, delete, store and forward themessages. When the end user accesses a message, the message can be readto the end user or can be displayed as textual information on acommunication device (e.g., a pager, a SMS 290, or a PDA, etc.). The enduser can also access and operate external messages or mail systemsremote from the electronic network 206.

[0089] The FAX server unit 272 is preferably connected to the telephoneswitch 230 and the LAN 240. The FAX server unit 272 receivers and storesfacsimile information sent via the electronic network 206 or the carriernetwork 216. Subscribers can access the facsimile information to play,store, delete, and forward the information. The facsimile informationcan be read via the TTS unit 252 or can be displayed as textualinformation on a suitable communication device. The FAX server unit 272preferably comprises a PC, such as, for example, a Windows NT compatiblePC or a Dialogue Fax Server.

[0090] Further information regarding communication system 200 isdisclosed in U.S. patent application Ser. No. 09/141,485, entitledTelecommunication System and Methods Therefor, filed Aug. 27, 1998, theentire disclosure of which is incorporated herein.

[0091] It should be appreciated that the embodiments described above areto be considered in all respects only illustrative and not restrictive.The scope of the invention is indicated by the following claims ratherthan by the foregoing description. All changes that come within themeaning and range of equivalents are to be embraced within their scope.

We claim:
 1. A method of creating an email usage record comprising:receiving an input signal; creating an email usage record in response tothe input signal; creating an event jacket associated with the emailusage record; receiving a command to send an email message; receiving aconfirmation signal after the email message has been sent; and creatingan email leg jacket including at least one record, the at least onerecord including information relating to the email message.
 2. Themethod of claim 1, wherein the input signal is received from acommunication device.
 3. The method of claim 2, wherein thecommunication device includes one of a telephone, a paging unit, acellular telephone, a satellite telephone, an Internet telephone and apersonal computer.
 4. The method of claim 1, wherein the instructionsignal is received at a communication node from a communication device.5. The method of claim 1, wherein the instruction signal is generated bya communication node.
 6. The method of claim 1, wherein the confirmationsignal is received at a communication node.
 7. The method of claim 1,wherein the event jacket includes at least one of an end useridentification record, an end user device identification record, a firsttime record and a first date record.
 8. The method of claim 1, whereinthe email leg jacket includes at least one of an identifier record, adestination address record, a source address record, a size record, anattachment record, a provider record, an urgency record, a deliveryrecord, a class record, a reoccurrence record, a recipient record, asecond time record, a second date record, a delivery receipt record anda bill-to record.
 9. A system for creating an email usage recordcomprising: computer readable program code to receive an input signal;computer readable program code to create an email usage record inresponse to the input signal; computer readable program code to receivea request to send an email message; computer readable program code toreceive a confirmation signal after the email message has been sent; andcomputer readable program code to create an email leg jacket includingat least one record, the at least one record including informationrelating to the email message.
 10. The system of claim 9, wherein theinput signal is received from a communication device.
 11. The system ofclaim 10, wherein the communication device includes one of a telephone,a paging unit, a cellular telephone, a satellite telephone, an Internettelephone and a personal computer.
 12. The system of claim 9, whereinthe instruction signal is received at a communication node from acommunication device.
 13. The system of claim 9, wherein the instructionsignal is generated by a communication node.
 14. The system of claim 9,wherein the confirmation signal is received at a communication node. 15.The system of claim 9, wherein the event jacket includes at least one ofan end user identification record, an end user device identificationrecord, a first time record and a first date record.
 16. The system ofclaim 9, wherein the email leg jacket includes at least one of anidentifier record, a destination address record, a source addressrecord, a size record, an attachment record, a provider record, anurgency record, a delivery record, a class record, a reoccurrencerecord, a recipient record, a second time record, a second date record,a delivery receipt record and a bill-to record.
 17. A program forcreating an email usage record comprising: computer readable programcode to receive an input signal; computer readable program code tocreate an email usage record in response to the input signal; computerreadable program code to receive a request to send an email message;computer readable program code to receive a confirmation signal afterthe email message has been sent; and computer readable program code tocreate an email leg jacket including at least one record, the at leastone record including information relating to the email message.
 18. Amethod of creating an email usage record comprising: creating an emailusage record; creating an event jacket associated with the email usagerecord; sending an email message; and creating an email leg jacketincluding at least one record associated with the email message.